fix(session): handle Qoder requires_action idle state and SSE reconnection#54
Merged
Conversation
…ction When Qoder agents execute tools, the session transitions through idle(requires_action) before resuming. Three issues caused session run to produce no output or hang: 1. Qoder mapper treated session.status_idle with stop_reason requires_action as terminal idle, causing poll/stream to exit before tool results and the final reply arrived. Fixed by mapping it to running. 2. streamWithResume did a single yield* of the SSE stream. When Qoder closes the SSE connection after requires_action, the generator exited without reconnecting. Added a reconnect loop with exponential backoff that continues until a true terminal status event arrives. 3. SSE parser in base-client discarded the id: field from SSE frames, so event.id was always undefined and stream reconnection could not skip already-consumed events. Now extracts id: and injects it into the parsed payload. Additionally, polling in collectEventsUntilTerminal now uses exponential backoff (300ms initial, doubling to 2s cap) instead of a fixed 2s interval, reducing first-response latency. Change-Id: Ieefe7ad827516f92fcfff3023600564d9eff0eec Co-developed-by: OpenCode <noreply@opencode.ai>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
agents session runproduced no output (or hung indefinitely) when the Qoder agent needed to execute tools (e.g. Bash). The command would exit prematurely after receiving onlythinking+tool_useevents, missing the tool results and the final assistant reply.Root Cause
Four interrelated issues:
Mapper:
requires_actiontreated as terminal — Qoder mapper mapped allsession.status_idleevents tostatus: "idle", which is a terminal status. Butidlewithstop_reason=requires_actionmeans the agent paused for tool execution and will resume. Poll/stream exited on the firstidlebefore tool results arrived.Stream: no SSE reconnection —
streamWithResumedid a singleyield*of the SSE stream. When Qoder closes the SSE connection afterrequires_action, the generator exited without reconnecting for subsequent events (tool_result, final message).SSE parser:
id:field discarded —BaseApiClient.sse()only parseddata:lines, ignoring the SSEid:field. This madeevent.idalwaysundefined, so stream reconnection could not useafter_idto skip already-consumed events.Polling: fixed 2s interval —
collectEventsUntilTerminalused a fixed 2-second polling interval, adding unnecessary latency for fast responses.Fix
qoder/mapper.tssession.status_idle + requires_action→"running"(non-terminal); extractraw.id→event.idbase-client.tsid:lines and inject into yielded objectssession-runtime.tsstreamWithResume: reconnect loop with exponential backoff until terminal status;collectEventsUntilTerminal: exponential backoff (300ms → 2s) instead of fixed 2ssession-event-mappers.test.tsrequires_actionmappingPerformance
Remaining latency is dominated by Qoder BYOC tool execution time (server-side), not client-side overhead.